Method and apparatus for communicating a data communication with an offset

ABSTRACT

A first indication can be received from at least one first of a first set of TRPs of a network. The first indication can indicate a minimum scheduling offset (Kmin) value between scheduling DCI of the first set of TRPs and a corresponding data communication. A second indication indicating the Kmin value can be indicated to at least one second TRP of a second set of TRPs of the network. First and second scheduling DCI can be received scheduling respective first and second data communications associated with the respective first and second sets of TRPs. The first and second data communications can be communicated with the respective first and second sets of TRPs of the network such that the offset between the first scheduling DCI and the first data communication is at least the Kmin value and the offset between the second scheduling DCI and the second data communication is at least the Kmin value.

BACKGROUND 1. Field

The present disclosure is directed to a method and apparatus forcommunicating a data communication with an offset. More particularly,the present disclosure is directed to communicating a data communicationwith an offset from scheduling downlink control information on awireless wide area network.

2. Introduction

Presently, wireless communication devices, such as User Equipment (UE),communicate with other communication devices using wireless signals.When a UE is not expected to receive or transmit over a time duration,it can go into a micro-sleep mode, where the UE can save power by goinginto a low power state, such as in Radio-Frequency (RF) components, inits front-end, in other modem hardware, and/or in other components. TheUE can extend the micro-sleep duration if the UE knows that the PhysicalDownlink Shared Channel (PDSCH) corresponding to a Physical DownlinkControl Channel (PDCCH), the PDCCH containing scheduling DownlinkControl Information (DCI), will not start before finishing decoding ofthe PDCCH via avoiding unnecessary buffering of Orthogonal FrequencyDivision Multiplexing (OFDM) symbols, such as for potential PDSCH, afterthe PDCCH is received but before the PDCCH is decoded. For example,micro-sleep duration can be extended if the PDSCH corresponding to thePDCCH, the PDCCH containing scheduling DCI, in slot ‘n’, will occur inslot ‘n+k0’, which is referred to as cross-slot scheduling, where k0>0for all k0 values in the associated Time-Domain Resource Allocation(TDRA) table, such as Table 5.1.2.1.1-2 in Technical Specification TS38.214. The minimum K0 value can be decided by the network based on someUE feedback/assistance, such as UE capability signaling, as power savingis highly related to UE implementation, and may be different fordifferent Subcarrier Spacings (SCS).

Once the UE goes into the power saving mode, such as extendedmicro-sleep which may occur in case of a traffic burst, it is desired toavoid scheduling delays, such as via switching from cross-slotscheduling back to same-slot scheduling, where scheduling DCI and thecorresponding scheduled PDSCH are in the same slot. One way to realizedynamic switching between power saving mode and non-power saving mode,such as cross-slot scheduling versus same-slot scheduling, is toindicate min K0 explicitly or implicitly in scheduling DCI, viaindicating a subset of TDRA table entries or indicating different TDRAtables from a set of configured TDRA table.

A deployment scenario where multiple Transmission/Reception Points(TRPs) can transmit/receive data to/from a UE could lead to bettercommunication, such as multi-TRP provides diversity, and hence morereliable communication. Depending on backhaul delay/latency with respectto joint dynamic scheduling, two general scenarios of multi-TRP withideal backhaul, such as joint scheduling possible as backhaul delay issmall, and multi-TRP with non-ideal backhaul exist, such as jointscheduling is not possible because of large backhaul delay. Fornon-ideal backhaul, each TRP/panel transmission can be scheduled via aseparate PDCCH, and multiple TRPs may only have semi-static coordinationand distributed scheduling. For ideal backhaul, all or a set ofmulti-TRP/panel transmissions can be scheduled via a single DCI/PDCCH.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which advantages and features of thedisclosure can be obtained, a description of the disclosure is renderedby reference to specific embodiments thereof which are illustrated inthe appended drawings. These drawings depict only example embodiments ofthe disclosure and are not therefore to be considered to be limiting ofits scope. The drawings may have been simplified for clarity and are notnecessarily drawn to scale.

FIG. 1 is an example block diagram of a system according to a possibleembodiment;

FIG. 2 is an example illustration a timeline where a PDCCH is receivedaccording to a possible embodiment;

FIG. 3 is an example flowchart illustrating the operation of a wirelesscommunication device according to a possible embodiment;

FIG. 4 is an example flowchart illustrating the operation of a wirelesscommunication device according to a possible embodiment;

FIG. 5 is an example flowchart illustrating the operation of a wirelesscommunication device according to a possible embodiment;

FIG. 6 is an example flowchart illustrating the operation of a wirelesscommunication device according to a possible embodiment; and

FIG. 7 is an example block diagram of an apparatus according to apossible embodiment.

DETAILED DESCRIPTION

Embodiments provide a method and apparatus for communicating a datacommunication with an offset with respect to a scheduling commandscheduling the data communication for power saving. At least someembodiments can provide power saving for multi-TRP operation. Accordingto a possible embodiment, a minimum scheduling offset value betweenscheduling DCI and a corresponding data communication can be determinedbased on a control channel configuration. Particular scheduling DCIscheduling a particular corresponding data communication can bereceived. A determination can be made regarding whether the determinedKmin value is applicable to the particular scheduling DCI and theparticular corresponding data communication. The particularcorresponding data communication can be communicated with a network suchthat the offset between the particular scheduling DCI and the particularcorresponding data communication is at least the determined Kmin value.

According to a possible embodiment, a first indication can be receivedfrom at least one first Transmission Reception Point (TRP) of a firstset of TRPs of a network. The first indication can indicate a minimumscheduling offset value (Kmin value) between scheduling DCI of the firstset of TRPs and a corresponding data communication. A second indicationcan be indicated to at least one second TRP of a second set of TRPs ofthe network. The second indication can indicate the Kmin value. A firstscheduling DCI can be received scheduling a first corresponding datacommunication associated with the first set of TRPs. A second schedulingDCI can be received scheduling a second corresponding data communicationassociated with the second set of TRPs. The first corresponding datacommunication can be communicated with the first set of TRPs of thenetwork such that the offset between the first scheduling DCI and thefirst corresponding data communication is at least the Kmin value. Thesecond corresponding data communication can be communicated with thesecond set of TRPs of the network such that the offset between thesecond scheduling DCI and the second corresponding data communication isat least the Kmin value.

FIG. 1 is an example block diagram of a system 100 according to apossible embodiment. The system 100 can include a UE 110, at least onenetwork entity 120 and 125, and a network 130. The UE 110 can be awireless wide area network device, a user device, a wireless terminal, aportable wireless communication device, a smartphone, a cellulartelephone, a flip phone, a personal digital assistant, a smartwatch, apersonal computer, a tablet computer, a laptop computer, a selectivecall receiver, an Internet of Things (IoT) device, or any other userdevice that is capable of sending and receiving communication signals ona wireless network. The at least one network entity 120 and 125 can be awireless wide area network base station, can be a NodeB, can be anenhanced NodeB (eNB), can be a New Radio (NR) NodeB (gNB), such as aFifth Generation (5G) NodeB, can be an unlicensed network base station,can be an access point, can be a base station controller, can be anetwork controller, can be a Transmission and Reception Point (TRP), canbe a different type of network entity from the other network entity,and/or can be any other network entity that can provide wireless accessbetween a UE and a network.

The network 130 can include any type of network that is capable ofsending and receiving wireless communication signals. For example, thenetwork 130 can include a wireless communication network, a cellulartelephone network, a Time Division Multiple Access (TDMA)-based network,a Code Division Multiple Access (CDMA)-based network, an OrthogonalFrequency Division Multiple Access (OFDMA)-based network, a Long TermEvolution (LTE) network, a NR network, a 3rd Generation PartnershipProject (3GPP)-based network, a 5G network, a satellite communicationsnetwork, a high altitude platform network, the Internet, and/or othercommunications networks.

In operation, the UE 110 can communicate with the network 130 via atleast one network entity 120. For example, the UE 110 can send andreceive control signals on a control channel and user data signals on adata channel.

At least some embodiments can provide methods to enable power saving viacross-slot scheduling in a multi-TRP setup. Since extended micro sleepcan depend on the PDCCH decoding time, the UE feedback/assistance mayneed to take into account the number of TRPs. Multiple PDCCHscorresponding to multiple TRPs may need to be decoded in a slot, such asin case of non-ideal backhaul or ideal backhaul but with PDCCHrepetition.

In some embodiments, different UE capabilities for a minimum K0 valuecan be signaled based on the number of TRPs, the UE can indicate to theother TRPs if UE configuration for one TRP results in the UE goinginto/out-of-power saving mode, and the minimum K0 value can becoordinated amongst TRP semi-statically.

Power saving can also be also applicable for other signals instead ofPDSCH, such as similar arguments as above may be applicable for avoidingunnecessary buffering of aperiodic Channel State Information ReferenceSignal (CSI-RS), Physical Uplink Shared Channel (PUSCH) and SoundingReference Signal (SRS), etc.

At least some embodiments can provide for power saving via cross-slotscheduling. In at least some embodiments, the cross-slot schedulingoperation can be modified to enable power saving. Cross-slot schedulingcan be possible via PDSCH time-domain resource allocation (TDRA) tablesdefined in TS 38.214, Tables 5.1.2.1.1-2-4. In particular, a TDRA table,which can contain e.g., up to 16 TDRA patterns per Bandwidth Part (BWP)can be configured by Radio Resource Control (RRC) signaling, andscheduling DCI indicates which entry of the TDRA table can be applicableto the scheduled PDSCH. Each entry of the TDRA table can include ofthree fields: K0, PDSCH mapping type, and StartSymbolAndLength. K0 canbe the time gap between PDCCH and PDSCH in unit of slots. K0=0 can implysame-slot scheduling and K0>0 can imply cross-slot scheduling. Mappingtype can refer to the mapping of the PDSCH. PDSCH-mapping-type-A canalso be referred to as slot based. PDSCH-mapping-type-B can also bereferred to as mini-slot based. startSymbolAndLength can indicate thestarting symbol index and duration of PDSCH within a slot.

FIG. 2 is an example illustration 200 a timeline where a PDCCH isreceived according to a possible embodiment. Cross-slot scheduling canbe supported by configuring a TDRA table with the minimum K0>0. Then,the UE can avoid unnecessary PDSCH buffering while the PDCCH can bedecoded leading to power saving. For example, if UE knows K0>0 beforePDCCH decoding, there can be no need to perform unnecessary PDSCHbuffering while the PDCCH being decoded.

From a latency perspective, same-slot scheduling, or in general havingno gap or small gap between PDCCH and PDSCH can be used. In case of aDownlink (DL) traffic burst, it can be useful to switch back tosame-slot scheduling from cross-slot scheduling. To avoid delay due toRRC reconfiguration signaling such as between cross-slot and same-slotscheduling, dynamic signaling can be used to determine a minimum K0value.

In some embodiments for an active DL and an active UL BWP, a UE can beindicated via signaling from a gNB to adapt the minimum applicablevalue(s) of K0, K2 and/or aperiodic CSI-RS triggering offsetwith/without QCL_typeD configured where the signaling type can bedown-selected from at least Medium Access Control (MAC) Control Element(CE) based and Layer 1 (L1) based signaling types.

In some embodiments, indication methods to adapt the minimum applicablevalue of K0 or K2 for an active DL or UL BWP, can include an indicationof a subset of TDRA entries, such as a bit-map based indication. Anotherindication method can include an indication of one active table frommultiple configured TDRA tables. Another indication method can includean indication of the minimum applicable value. In some embodiments PDCCHmonitoring case 1-1 can be prioritized.

In at least some embodiments, adapting the minimum applicable value ofthe aperiodic CSI-RS triggering offset for an active DL BWP, can beindicated by an implicit indication by defining the minimum applicablevalue the same as the minimum applicable K0 value when indicated. Insome embodiments adapting the minimum applicable value of the aperiodicCSI-RS triggering offset for an active DL BWP can be an indication ofthe minimum applicable value. In some embodiments the PDCCH monitoringcase 1-1 can be prioritized for the design.

In at least some embodiments, the adaptation on the minimum applicablevalue of K0 may not apply to at least some of the cases in Table 1,where RNTI is Radio Network Temporary Identifier, SI is SystemInformation, RA is Random Access, TC is Temporary Cell, and P is Paging.

TABLE 1 RNTI PDCCH search space SI-RNTI Type0 common SI-RNTI Type0Acommon RA-RNTI, TC-RNTI Type1 common P-RNTI Type2 common

In at least some embodiments for aperiodic CSI-RS triggering, at leastif a UE is operated with cross-slot scheduling based power saving if allof the associated trigger states do not have the higher layer parameterqcl-Type set to ‘QCL-TypeD’ in the corresponding TransmissionConfiguration Indication (TCI) states and the PDCCH SCS is equal to theCSI-RS SCS, then the aperiodic CSI-RS triggering offset can be set to anon-zero value.

In some embodiments when the UE is scheduled to receive PDSCH by a DCI,the Time domain resource assignment field value m of the DCI can providea row index m+1 to an allocation table. The determination of the usedresource allocation can be defined in sub-clause 5.1.2.1.1 of TS 38.214.The indexed row can define the slot offset K0, the start and lengthindicator SLIV, or directly the start symbol S and the allocation lengthL, and the PDSCH mapping type to be assumed in the PDSCH reception.

In some embodiments given the parameter values of the indexed row, theslot allocated for the PDSCH can be

${\left\lfloor {n \cdot \frac{2^{\mu_{PDSCH}}}{2^{\mu\;{PDCCH}}}} \right\rfloor + K_{0}},$where n can be the slot with the scheduling DCI, and K0 can be based onthe numerology of PDSCH, and μ_(PDSCH) and μ_(PDCCH) can be thesubcarrier spacing configurations for PDSCH and PDCCH, respectively.Also, the starting symbol S relative to the start of the slot, and thenumber of consecutive symbols L counting from the symbol S allocated forthe PDSCH can be determined from the start and length indicator SLIV.For example,

if (L−1)≤7 thenSLIV=14·(L−1)+SelseSLIV=14·(14−L+1)+(14−1−S)

where 0<L≤14−S.

Also, the PDSCH mapping type can be set to Type A or Type B as definedin sub-clause 7.4.1.1.2 of TS 38.211.

The UE can consider the valid Sand L combinations defined in Table 2 asvalid PDSCH allocations.

TABLE 2 PDSCH Normal cyclic prefix Extended cyclic prefix mapping type SL S + L S L S + L Type A {0, 1, 2, 3} {3, . . . , 14} {3, . . . , 14}{0, 1, 2, 3} {3, . . . , 12} {3, . . . , 12} (Note 1) (Note 1) Type B{0, . . . , 12} {2, 4, 7} {2, . . . , 14} {0, . . . , 10} {2, 4, 6} {2,. . . , 12} Note 1: S = 3 is applicable only if dmrs-TypeA-Position = 3

In at least some embodiments multi-TRP operation can enhance thecommunication reliability. Each TRP can be associated with a TCI state,and a single PDCCH, such as typically used for ideal/low-latencybackhaul among TRPs, can be used to schedule PDSCH(s) associated withdifferent TRPs. For non-ideal backhaul among TRPs different PDCCHs canschedule different PDSCHs corresponding to different TRPs. For ensuringhigh reliability of PDCCH, the same DCI can be signaled via differentTRPs.

A UE can be higher-layer configured with a list of up to M TCI-Stateconfigurations to decode PDSCH intended for the UE in a serving cell,where M can depend on the UE capability. Each TCI-State can containparameters for configuring a quasi-co-location relationship between oneor two downlink reference signals and the Demodulation Reference Symbol(DM-RS) ports of the PDSCH. The quasi co-location relationship can beconfigured by the higher layer parameter qcl-Type1 for the firstDownlink (DL) Reference Signal (RS), and qcl-Type2 for the second DL RS,if configured. For the case of two DL RSs, the Quasi Co-Location (QCL)types can be not the same, regardless of whether the references are tothe same DL RS or different DL RSs. The quasi co-location typescorresponding to each DL RS can be given by the higher layer parameterqcl-Type in QCL-Info and can take one of the following values:

‘QCL-TypeA’: {Doppler shift, Doppler spread, average delay, delayspread}

‘QCL-TypeB’: {Doppler shift, Doppler spread}

‘QCL-TypeC’: {Doppler shift, average delay}

‘QCL-TypeD’: {Spatial Rx parameter}

In at least some embodiments a UE can be configured with the higherlayer parameter tci-PresentInDCI that can be set as ‘enabled’ for theControl Resource Set (CORESET) scheduling the PDSCH, and the UE canassume that the TCI field is present in the DCI format 1_1 of the PDCCHtransmitted on the CORESET. If tci-PresentInDCI is not configured forthe CORESET scheduling the PDSCH or the PDSCH is scheduled by a DCIformat 1_0, and the time offset between the reception of the DL DCI andthe corresponding PDSCH is equal to or greater than a thresholdThreshold-Sched-Offset, where the threshold can be based on reported UEcapability, for determining PDSCH antenna port quasi co-location, thenthe UE can assume that the TCI state or the QCL assumption for the PDSCHcan be identical to the TCI state or QCL assumption, whichever isapplied for the CORESET used for the PDCCH transmission. If thetci-PresentInDCI is set as ‘enabled’, then the TCI field in DCI in thescheduling component carrier can point to the activated TCI states inthe scheduled component carrier or DL BWP and when the PDSCH isscheduled by DCI format 1_1, the UE can use the TCI-State according tothe value of the ‘Transmission Configuration Indication’ field in thedetected PDCCH with DCI for determining PDSCH antenna port quasico-location. The UE can assume that the DM-RS ports of PDSCH of aserving cell are quasi co-located with the RS(s) in the TCI state withrespect to the QCL type parameter(s) given by the indicated TCI state ifthe time offset between the reception of the DL DCI and thecorresponding PDSCH is equal to or greater than a thresholdThreshold-Sched-Offset, where the threshold can be based on reported UEcapability.

In at least some embodiments, candidate schemes for multi-TRP basedUltra Reliable Low Latency Communication (URLLC) can be scheduled by atleast a single DCI where n (n<=N_(s)) TCI states can be within thesingle slot with overlapped time and frequency resource allocation,where each transmission occasion can be a layer or a set of layers ofthe same Transport Block (TB), with each layer or layer set can beassociated with one TCI and one set of DMRS port(s), and single codewordwith one Redundancy Version (RV) can be used across all spatial layersor layer sets. From the UE perspective, different coded bits can bemapped to different layers or layer sets with the same mapping rule asin Rel-15 of 3GPP. In at least some embodiments, each transmissionoccasion can be a layer or a set of layers of the same TB, with eachlayer or layer set can be associated with one TCI and one set of DMRSport(s), where a single codeword with one RV can be used for eachspatial layer or layer set. The RVs corresponding to each spatial layeror layer set can be the same or different. In another embodiment onetransmission occasion can be one layer of the same TB with one DMRS portassociated with multiple TCI state indices, or one layer of the same TBwith multiple DMRS ports associated with multiple TCI state indices oneby one, and applying different MCS/modulation orders for differentlayers or layer sets can be selected.

In at least some embodiments, candidate schemes for multi-TRP basedURLLC can be scheduled by at least a single DCI where n (n<=N_(s)) TCIstates can be within the single slot with overlapped time and frequencyresource allocation. Where n (n<=N_(f)) TCI states can be within thesingle slot, with non-overlapped frequency resource allocation, whereeach non-overlapped frequency resource allocation can be associated withone TCI state, same single/multiple DMRS port(s) can be associated withall non-overlapped frequency resource allocations. In another embodimentsingle codeword with one RV can be used across full resource allocation.From a UE perspective, the common RB mapping, such as codeword to layermapping as in Rel-15, can be applied across full resource allocation. Inother embodiments a single codeword with one RV can be used for eachnon-overlapped frequency resource allocation, the RVs corresponding toeach non-overlapped frequency resource allocation can be the same ordifferent. Applying different MCS/modulation orders for differentnon-overlapped frequency resource allocations can be selected, and afrequency resource allocation mechanism for FDM 2 a/2 b with regardingto allocation granularity, time domain allocation can be determined.

In at least some embodiments, candidate schemes for multi-TRP basedURLLC can be scheduled by at least a single DCI where n (n<=N_(s)) TCIstates can be within the single slot with overlapped time and frequencyresource allocation, where n (n<=N_(t1)) TCI states within the singleslot, with non-overlapped time resource allocation, and eachtransmission occasion of the TB can have one TCI and one RV with thetime granularity of mini-slot. All transmission occasion(s) within theslot can use a common Modulation and Coding Scheme (MCS) with the samesingle or multiple DMRS port(s), and RV/TCI state can be the same ordifferent among transmission occasions. Channel estimation interpolationcan be performed across mini-slots with the same TCI index.

In at least some embodiments for TDM, where n (n<=N_(t2)) TCI stateswith K (n<=K) different slots, each transmission occasion of the TB canhave one TCI and one RV, all transmission occasion(s) across K slots canuse a common MCS with same single or multiple DMRS port(s), RV/TCI statecan be same or different among transmission occasions, and channelestimation interpolation can be performed across slots with the same TCIindex.

In at least some embodiments, M-TRP/panel based URLLC schemes can becompared in terms of improved reliability, efficiency, and specificationimpact, and support of number of layers per TRP can be discussed.

In some embodiments, to support multiple-PDCCH based multi-TRP/paneltransmission with intra-cell with the same cell ID, and inter-cell withdifferent Cell IDs, a RRC configuration can be used to link multiplePDCCH/PDSCH pairs with multiple TRPs where one CORESET in a“PDCCH-config” can correspond to one TRP.

In one embodiment, the UE can indicate a first and a second capabilityfor minimum value of a scheduling offset, such as a time gap between theend of the scheduling PDCCH and the beginning of the correspondingPDSCH, referred to as K0_min, to the network. The first capability canbe associated with single-TRP operation and the second capability can beassociated with multi-TRP operation.

The following embodiments can be dependent or independent embodimentswith respect to each other. The first K0_min which can correspond to thefirst capability signal can be smaller than the second K0_mincorresponding to the second capability signaling. The UE can indicatevia scheduling PDCCH an entry of a TDRA table. In some embodiments, ifthe corresponding K0 is smaller than the applicable K0_min then the UEmay not expect to be scheduled with that TDRA entry. In one embodiment,the UE can be expected to not receive PDSCH corresponding to thescheduling PDCCH indicating that TDRA entry. In another embodiment, forPUSCH instead of PDSCH, K2_min can be used instead of K0_min, and if theUE is indicated via scheduling PDCCH an entry of an UL TDRA table, ifthe corresponding K2 is smaller than the applicable K2_min, then the UEmay not expect to be scheduled with that TDRA entry. In an alternateembodiment, if high priority data comes in the UL buffer and isindicated by a Buffer Status Report (BSR), then the UE, upon receptionof PDCCH indicating an Uplink (UL) TDRA table entry with correspondingK2 being smaller than the applicable K2_min, can follow the indicated ULTDRA, where the DCI indication of K2 smaller than K2_min can be allowed.

In at least some embodiments, K0_min can be determined based on the UEcapability signaling. In case different K0_min UE capabilities fordifferent scenarios are indicated, the UE can determine the applicableK0_min based on the scenario for which K0_min UE capability is defined.If the UE is configured to monitor a first number of maximum CORESETsper “PDCCH-config”, referred to as ‘m1,’ such as 3, then the UE candetermine the applicable K0_min based on the first K0_min. If the UE isconfigured to monitor a second number of maximum CORESETs per“PDCCH-config”, referred to as ‘m2’, such as 5, then the UE candetermine the applicable K0_min based on the second K0_min, where m1<m2.If the maximal number of BD/CCE per slot per serving cell for the UE is‘W1’, then the UE can determine the applicable K0_min based on the firstK0_min. If the maximal number of BD/CCE per slot per serving cell forthe UE is ‘W2’, then the UE can determine the applicable K0_min based onthe second K0_min, where W1<W2. If the UE is configured with a first setof CORESET/search space parameters, then the UE can determine theapplicable K0_min based on the first K0_min.

In at least some embodiments, if the UE is configured with a second setof CORESET/search space parameters, such asmonitoringSlotPeriodicityAndOffset, then the UE can determine theapplicable K0_min based on the second K0_min.

In at least some embodiments, if the number of CORESETs to be monitored,such as CORESETs with monitored search space, in a slot and/orCORESET(s) duration is smaller than a threshold, then the UE candetermine the applicable K0_min based on the first K0_min.

In at least some embodiments, if the number of CORESETs to be monitoredin a slot and/or CORESET(s) duration is larger than the threshold, thenthe UE can determine the applicable K0_min based on the second K0_min.

In at least some embodiments, a multi-PDCCH, such as for multi-TRP,capable UE can have higher processing capability compared to a UE thatis not capable of multi-TRP operation, and in that case a UE capability,such as irrespective to whether multi-TRP operation is enabled or not,can indicate a K0_min value for the purpose of power saving. The UE canindicate the second capability, such as for minimum value of thescheduling offset, if the processing capability of multi-TRP capable UEis not noticeably higher than the processing capability of non-multi-TRPcapable UE. The processing capability can be the PDSCH processingcapability used in TS 38.214, such as PDSCH processing capability 1 and2 related to PDSCH decoding time N1 symbols, or the PDCCH processingcapability for instance indicated by pdcch-BlindDetectionCA capabilityused in TS 38.213. In one embodiment, if a UE is not configured withmulti-TRP operation, a first PDSCH/PDCCH processing capability isapplicable, and if the UE is configured with multi-TRP operation, asecond PDSCH/PDCCH processing capability is applicable, then only thefirst capability for minimum value of the scheduling offset can be used.If the first and the second PDSCH/PDCCH processing capabilities are thesame, then the first and the second capabilities for minimum value ofthe scheduling offset can be used.

The UE can indicate a third capability for minimum value of a schedulingoffset, such as a time gap between the end of the scheduling PDCCH andthe beginning of the corresponding PDSCH, referred to as K0_min, to thenetwork. The second capability can be associated with multi-TRPoperation with ‘M1’ TRPs, or up to M1-TRPs, and the third capability canbe associated with multi-TRP operation with ‘M2’ TRPs or from M1+1 up toM2 TRPs, where M1<M2, and number of TRPs can be configured. The maximumnumber of TRPs/TCI states a UE can simultaneously have PDSCHtransmissions associated can be configured by higher layer signaling.

In an alternate embodiment, the UE can indicate only the firstcapability for minimum value of the scheduling offset, and in casemulti-TRP operation is configured/enabled, an offset can be added to theindicated K0_min value. The offset can be fixed in the specification fordifferent PDSCH processing capabilities, such as fraction of N1 or N2values, or signaled as capability, such as a fraction of N1 or N2, oroffset value for a reference subcarrier spacing. N2 can be a PUSCHpreparation/processing time, as understood to one of ordinary skill inthe art. In an embodiment, the offset to K0_min value can be appliedwhen multi-DCI/multi-PDCCH is used, such as for multi-TRP operation, andif single PDCCH is used to schedule PDSCHs associated to multiple TRPs,the same K0_min value can be applicable.

In another embodiment, if PDSCHs associated with a first TRP areexpected to be scheduled with a K0_min>0, such as via determination ofK0_min based on the scheduling PDCCH or MAC-CE signaling, for example inthe case of non-ideal backhaul, the UE can indicate to other TRPs thatthe first TRP has indicated K0_min>0 so that other TRPs can lead topower saving or the other way around if PDSCHs associated with the firstTRP are expected to be scheduled with a K0_min=0, such as viadetermination of K0_min based on the scheduling PDCCH or MAC-CEsignaling, such as in case of non-ideal backhaul, UE can indicate toother TRPs that the first TRP has indicated K0_min=0 so that other TRPscan benefit from same-slot scheduling with smaller scheduling latencythan the latency due to cross-slot scheduling.

The following related embodiments can be dependent or independentembodiments with respect to each other. The UE can indicate via PUCCH ifK0_min is larger than ‘0’ at least for ‘n’ TRPs, such as identified bydifferent CORESETs, where ‘n’ can be configurable/fixed in thespecifications, such as one, can depend on the number of TRPs orCORESETs, and/or can depend on the value of K0_min.

In one embodiment, if a UE receives an indication that a PDSCH from afirst TRP or a PDSCH associated with a first TCI state, or a PDSCHassociated with/scheduled by a PDCCH detected in a first search space ofa first CORESET, is scheduled with a K0_min>0, such as cross-slotscheduling based power saving mode is enabled for the first TRP/firstTCI state/first search space/first CORESET, the UE can assume that a DLassignment DCI format/PDCCH detected in any of CORESETs, which can bemonitored in a slot where the first CORESET, the first search space ismonitored, carries PDSCH scheduling information with K0_min>0. The UEcan be not expected to receive different K0_min indications applicableto a slot. Even in non-ideal backhaul, multiple TRPs can coordinatesemi-statically, such as in every 10 msec, for scheduling and otherconfiguration information. Thus, semi-static power saving modeoperation, such as enabling/disabling of cross-slot scheduling basedpower saving mode for a given CORESET/search space is donesemi-statically, can be coordinated among the cooperating TRPs.

In another embodiment, if a UE receives an indication that a PDSCH froma first TRP, or a PDSCH associated with a first TCI state, or a PDSCHassociated with/scheduled by a PDCCH detected in a first search space ofa first CORESET, and is scheduled with a K0_min>0, such as cross-slotscheduling based power saving mode is enabled for the first TRP/firstTCI state/first search space/first CORESET, and if a PDSCH from a secondTRP, or a PDSCH associated with a second TCI state, or a PDSCHassociated with/scheduled by a PDCCH detected in a second search spaceof a second CORESET is configured to be always scheduled with K0_min=0,such as cross-slot scheduling is not allowed for the second TRP/secondTCI state/second search space/second CORESET for the UE, then the UE canassume that in a slot where the UE monitors both the first CORESET/firstsearch space and the second CORESET/second search space, cross-slotscheduling based power saving mode operation can be disabled for thefirst TRP/first TCI state/first search space/first CORESET. In oneembodiment, the PDSCH from the second TRP, or associated with the secondTCI state, or associated with/scheduled by a PDCCH detected in thesecond search space of the second CORESET, can carry URLLC traffic,which can be always scheduled with same-slot scheduling.

In an embodiment, if a UE receives a traffic type/priority/latencyindication, such as via scheduling DCI, then the UE can assume thecross-slot scheduling, K0_min>0 indication is not applicable anymoreuntil the UE receives another cross-slot scheduling, K0_min>0indication.

In an embodiment, if a UE is configured with DL SPS operation with theperiodicity of ‘m’ slots or if a DL SPS operation with the periodicityof ‘m’ slots is activated, such as by a DCI, the UE can assumes thecross-slot scheduling with k0_min<m is not possible, and the UE can benot expected to receive cross-slot scheduling, K0_min>0, indication withk0_min<m. The value of ‘m’ can be smaller than a threshold. Thethreshold can be a UE capability/configured via higherlayers/dynamically indicated or fixed. In an embodiment, if the UE isconfigured with an SPS operation with short periodicity, the UE can benot expected to be scheduled with DL SPS PDSCH in the same slot or in aslot that is less than the indicated K0_min value with respect to theslot in which the activation DCI is received.

In an embodiment, the UE can be indicated a first minimum value of thescheduling offset, such as K0_min value which can be signaled via PDCCHor MAC-CE and can be for power saving operation. The UE can determinethe K0_min value applicable to a slot based on the first K0_min valueand the PDCCH processing capability of the UE if the UE is configuredwith multi-TRP operation, and if the UE is monitoring multiple CORESETs,or search spaces in multiple CORESETs, where each CORESET can correspondto a TRP or a set of TRPs for multi-TRP operation.

In an embodiment, the K0_min value applicable to the slot can bedetermined by adding an offset, which can be positive, negative, orzero, to the first K0_min value. The offset can be fixed in thespecification for different PDSCH processing capabilities, such asfraction of N1 or N2 values, or signaled as a capability, such as afraction of N1 or N2, or offset value for a reference subcarrierspacing. For multiple PDCCH in different CORESETS, such as for multi-TRPoperation when the UE can monitor multiple CORESETs or search spaces inmultiple CORESETs, where each CORESET can correspond to a TRP, or a setof TRPs, for multi-TRP operation, the number of symbols between theearliest CORESET and the latest CORESET, such as in a slot, can be addedto the offset. In an embodiment, the offset can be an integer value inthe unit of slots, and in another example, the offset can be an integervalue in the unit of symbols.

In an example, minimum K0 value can be determined for each slot based onan indication of cross-slot scheduling and the number of CORESETsassociated with different TCI states being monitored in the slot.

In one embodiment, a multi-PDCCH, for multi-TRP, capable UE can havehigher processing capability and can be able to support the same K0_minvalue for single-TRP operation and multi-TRP operation. The UE canindicate only a single minimum value of a scheduling offset, K0_min,which can be applicable to both single-TRP operation and multi-TRPoperation.

In one embodiment, the UE can indicate a first capability for minimumvalue of a scheduling offset, first K0_min, associated with single-TRPoperation. The multi-TRP operation associated K0_min, second K0_min,value can be determined based on an offset added to the first K0_min forsingle-PDCCH or single TRP operation. The offset can be in number ofslots, or symbols, instead of slots, with value depending on thesubcarrier spacing. The offset can be fixed in the specification fordifferent PDSCH processing capabilities, such as a fraction or scalingfactor of N1 or N2 values, or signaled as a second capability, such as afraction or scaling factor of N1 or N2 or offset value for a referencesubcarrier spacing, or can depend on the number of TRPs, or CORESETs,and can depend on the value of first K0_min. In one embodiment, if theUE is monitoring search space in multiple CORSETs in a slot, the numberof symbols between the earliest CORESET and the latest CORESET can beadded to the offset to determine the second K0_min value. The UE candetermine the applicable K0_min based on one or more of the variousembodiments described above for determining the applicable K0_min.

In some embodiments, the scheduling offset (K0_min) value can be for orcorrespond to a reference subcarrier spacing such as the subcarrierspacing for SIB1, or subcarrier spacing for the initial DL BWP or thelowest subcarrier spacing supported for that band. The K0_min value forother subcarrier spacing can be determined based on the indicated K0_minvalue and the reference subcarrier spacing, such as scaling factorsfixed in the specification or indicated in capability signaling. In oneexample, K0_min values for each of the subcarrier spacings supported forthe band can be indicated in the capability signaling.

In an embodiment, the cross-slot scheduling indication, such asindicating K0_min once received can be applicable to the next “T” slots,where “T” can be configured or UE capability or traffic dependent or DCIformat dependent. In another embodiment, if cross-slot scheduling forpower saving is configured/enabled, the UE can go into power savingmode, such as UE assumes a K0_min>0, unless it receives a DL schedulingDCI indicating a TDRA entry with K0=0. Upon such reception, a timer canbe triggered and can run for “R” slots and, while the timer is runningK0_min may not be assumed to be zero. Once the timer expires, the UE cango back to the power saving mode, such as by assuming K0_min>0.

In an embodiment, if the UE is configured with multi-TRP operation withmultiple PDCCHs being monitored in different search spaces of differentCORESETs associated to different TRPs/TCI states, and the differentsearch spaces are monitored in different slots, if there is a timer forcross-slot scheduling, then the initial value of timer can allow givingdifferent TRPs a chance to transmit, such as if there are 2 TRPs theinitial timer value can be a multiple of 2 slots. In another embodiment,the on-duration or the initial value of the inactivity timer ofDiscontinuous Reception (DRX) for a UE in units of slot can be amultiple of number of TRPs configured. In one embodiment, if the firstDL assignments associated with the first TRP is being monitored in oddslots and the second DL assignments associated with the second TRP isbeing monitored in even slots, then the timers for power saving or DRXtimers and on-duration can be set such that their initial value ends inan odd slot, such as by assuming the first slot index is slot 0. In anembodiment, for a UE configured with two TRPs, the DRX on-duration inunit of slot can be a multiple of 2 slots, and the DRX inactivity timermay only expire in odd slots assuming the DRX on-duration has started inan even slot.

According to a possible embodiment, a UE can indicate to the network, afirst and a second capability for a minimum value of a scheduling offsetbetween a scheduling DCI and the corresponding PDSCH. The firstcapability can be associated with single-TRP operation and the secondcapability can be associated with multi-TRP operation.

According to another possible embodiment, a UE can receive aconfiguration configuring the UE to communicate with the network via aset of TRPs. The UE can receive one or more indications from a firstsubset of the set of TRPs indicating that the minimum value of ascheduling offset associated with each TRP of the set of TRPstransmission is greater than zero. The UE can indicate to at least asecond subset of TRPs that the minimum value of a scheduling offsetassociated with a number of TRPs of the set of TRPs transmission isgreater than zero.

According to another possible embodiment, a UE can receive aconfiguration configuring the UE to communicate with the network via aset of TRPs. The UE can receive one or more indications from a firstsubset of the set of TRPs indicating that the minimum value of ascheduling offset associated with each TRP of the set of TRPstransmission is zero. The UE can indicate to at least a second subset ofTRPs that the minimum value of a scheduling offset associated with thetransmissions of the first subset of TRPs can be zero if the minimumvalue of a scheduling offset associated with the transmission(s) of anumber of TRPs of the set of TRPs is greater than zero.

According to another possible embodiment at a base station with a firstTRP and a second TRP, the base station can send a minimum value of ascheduling offset from the first TRP to the second TRP. The base stationcan send an indication from at least the second TRP to the UE indicatingthe minimum value of the scheduling offset. The base station cantransmit DL data, such as PDSCH, from both TRPs to the UE respecting theminimum value of the scheduling offset.

According to another possible embodiment, a UE can determine a minimumvalue of a scheduling offset between scheduling DCI and correspondingPDSCH based on an indication of a first minimum value of a schedulingoffset and the number of, the location of, and the duration of theCORESETs associated with different TCI states being monitored in theslot.

According to another possible embodiment, a UE can receive a DL SPSconfiguration with a SPS periodicity of ‘m’ slots, where ‘m’ can besmaller than a threshold, such as 10 ms. The UE can receive anindication of a minimum value of a scheduling offset between schedulingDCI and corresponding PDSCH. The UE can discard the indication afterreception of a SPS activation command in a slot.

According to another possible embodiment, a User Equipment (UE) canreceive an indication of a first minimum value of a scheduling offsetbetween scheduling DCI and corresponding PDSCH for PDSCHs scheduled viaPDCCHs being monitored in a first search space of a first CORESET. TheUE can assume PDSCH scheduling information in a second search space of asecond CORESET has a minimum value of a scheduling offset determinedbased on the first minimum value of a scheduling offset. The minimumvalue of a scheduling offset can be the same as the first minimum valueof a scheduling offset.

In some embodiments different UE capabilities for a minimum K0 value canbe signaled based on the number of TRPs.

In some embodiments the UE can indicate to the other TRPs if the UEconfiguration for a TRP results in the UE going into/out-of-power savingmode.

In some embodiments the minimum K0 value can be coordinated amongst TRPsemi-statically.

In some embodiments the minimum K0 value can be determined for each slotbased on an indication of cross-slot scheduling and the number ofCORESETs associated with different TCI states being monitored in theslot.

In some embodiments conditions where the indicated minimum K0 value isnot applicable/disabled can include SPS with short periodicityactivated/configured, reception of a URLLC scheduling DCI, and/orcross-slot scheduling is not being configured for one of the TRPs.

In some embodiments the minimum K0 value determination for PDSCHs of aset of TRPs can be based on the indicated minimum K0 value correspondingto PDSCHs of a different set of TRPs.

FIG. 3 is an example flowchart 300 illustrating the operation of awireless communication device, such as the UE 110, according to apossible embodiment. At 310, a minimum scheduling offset value (Kmin)between scheduling DCI and a corresponding data communication can bedetermined based on a control channel configuration. At 320, particularscheduling DCI can be received. The particular scheduling DCI canschedule a particular corresponding data communication.

At 330, a determination can be made as to whether the determined Kminvalue is applicable to the particular scheduling DCI and the particularcorresponding data communication. At 340, in response to determining thedetermined Kmin value is applicable to the particular scheduling DCI andthe particular corresponding data communication, the particularcorresponding data communication can be communicated with a network suchthat the offset between the particular scheduling DCI and the particularcorresponding data communication is at least the determined Kmin value.The offset can be a time offset.

According to a possible embodiment, the control channel configurationcan be a maximum number of CORESETs in a PDCCH configuration, alimitation on number of PDCCH blind decodes, a limitation on number ofCCEs for PDCCH monitoring, and/or any other control channelconfiguration. According to a possible embodiment, the determined Kminvalue can be further determined based on a PDCCH processing capability,a PDSCH processing capability, a PUSCH processing capability, and/or anyother information. For example, the offset can be fixed in thespecification for different PDSCH processing capabilities, such as fixedas fraction of N1 or N2 values, or signaled as UE capability signaling,such as signaled as a fraction of N1 or N2 or offset value for areference subcarrier spacing, and/or can be otherwise established. N1can be defined in tables 5.3-1 and 5.3-2 in section 5.3 of TS 38.214. N2can be defined in tables 6.4-1 and 6.4-2 in section 6.4 of TS 38.214.According to a possible embodiment, the determined Kmin value canfurther be determined based on an indication from the network.

According to a possible embodiment, an indication can be sent to thenetwork indicating that the UE is capable of power saving using a firstset of Kmin values associated with a first control channel parameter andusing a second set of Kmin values associated with a second controlchannel parameter. The determined Kmin value can be determined based onthe first set of Kmin values and the second set of Kmin values.According to a possible embodiment, a control channel parameter can be amaximum number of CORESETs in a PDCCH configuration, a limitation onnumber of PDCCH blind decodes, a limitation on number of CCEs for PDCCHmonitoring, a PDCCH processing capability, a PDSCH processingcapability, a PUSCH processing capability, and/or any other controlchannel parameter.

According to a possible embodiment, the particular scheduling DCI canindicate a scheduling offset (K) to apply between the particularscheduling DCI and the particular corresponding data communication. Thedetermined Kmin value can be applicable to the particular scheduling DCIand the particular corresponding data communication if the schedulingoffset (K) is equal to or larger than the determined Kmin value. Ascheduling DCI can schedule data communication. According to a possibleembodiment, the particular corresponding data communication may not becommunicated with the network based on the scheduling offset (K) beingless than the determined Kmin value.

According to a possible embodiment, a priority indication can bereceived in the particular scheduling DCI. The determined Kmin value canbe determined to not be applicable to the particular scheduling DCI andthe particular corresponding data communication. In response todetermining the determined Kmin value is not applicable to theparticular scheduling DCI and the particular corresponding datacommunication, the particular corresponding data communication can becommunicated with the network such that the offset between theparticular scheduling DCI and the particular corresponding datacommunication is smaller than the determined Kmin value.

According to a possible embodiment, the particular corresponding datacommunication can be a PDSCH data transmission. According to a possibleembodiment, the particular corresponding data communication can be anPUSCH data transmission.

According to a possible embodiment, an indication can be sent to thenetwork indicating that the UE is capable of power saving using aparticular Kmin value. The Kmin value can be determined by applying anoffset to the particular Kmin value. According to a possible embodiment,applying the offset to the particular Kmin value can include adding theoffset to the particular Kmin value when the UE monitors at least acertain number of CORESETs for PDCCH monitoring. According to a possibleembodiment, the offset can be determined based on a PDCCH processingcapability, a PDSCH processing capability, a PUSCH processingcapability, and/or other information.

FIG. 4 is an example flowchart 400 illustrating the operation of awireless communication device, such as the network entity 120, accordingto a possible embodiment. At 410, a control channel configuration can besent. The control channel configuration can determine a minimumscheduling offset value (Kmin) between scheduling DCI and acorresponding data communication. At 420, particular scheduling DCI canbe transmitted. The particular scheduling DCI can schedule a particularcorresponding data communication. At 430, the corresponding datacommunication can be communicated, based on the Kmin value beingapplicable to the particular scheduling DCI and the particularcorresponding data communication, with a user equipment such that theoffset between the particular scheduling DCI and the particularcorresponding data communication is at least the Kmin value. Otherreciprocal operations to the flowchart 300 can also be performed.

FIG. 5 is an example flowchart 500 illustrating the operation of awireless communication device, such as the UE 110, according to apossible embodiment. At 510, a first indication can be received from atleast one first TRP of a first set of TRPs of a network. The firstindication can indicate a minimum scheduling offset value (Kmin value)between scheduling DCI of the first set of TRPs and a corresponding datacommunication. At 520, a second indication can be indicated to at leastone second TRP of a second set of TRPs of the network. The secondindication can indicate the Kmin value. At 530, a first scheduling DCIcan be received. The first scheduling DCI can schedule a firstcorresponding data communication associated with the first set of TRPs.At 540, a second scheduling DCI can be received. The second schedulingDCI can schedule a second corresponding data communication associatedwith the second set of TRPs.

At 550, the first corresponding data communication can be communicatedwith the first set of TRPs of the network such that the offset betweenthe first scheduling DCI and the first corresponding data communicationis at least the Kmin value. At 560, the second corresponding datacommunication can be communicated with the second set of TRPs of thenetwork such that the offset between the second scheduling DCI and thesecond corresponding data communication is at least the Kmin value.

According to a possible embodiment, the first scheduling DCI can bereceived in a first CORESET of a first set of CORESETs. The secondscheduling DCI can be received in a second CORESET of a second set ofCORESETs. The first set of CORESETs and the second set of CORESETs canbe different. The first CORESET and the second CORESET can be different.

According to a possible embodiment, the first CORESET can be associatedwith a first TCI state, the second CORESET can be associated with asecond TCI state, and the first TCI state and the second TCI state canbe different.

According to a possible embodiment, the second indication can beindicated via a physical layer uplink control channel (PUCCH).

According to a possible embodiment, the first corresponding datacommunication can be a first PDSCH data transmission and the secondcorresponding data communication can be a second PDSCH datatransmission.

According to a possible embodiment, the first corresponding datacommunication can be a first PUSCH data transmission and the secondcorresponding data communication can be a second PUSCH datatransmission.

According to a possible embodiment, the Kmin value can be zero.According to a possible embodiment, the Kmin value can be greater thanzero.

According to a possible embodiment, the first scheduling DCI schedulingcan be received in a slot. The second scheduling DCI can be received inthe same slot as the first scheduling DCI.

According to a possible embodiment, the first corresponding datacommunication can be communicated in a slot. The second correspondingdata communication can be communicated in the same slot as the firstcorresponding data communication.

According to a possible embodiment, the first downlink PDSCH can beassociated with a first TCI state. The second downlink PDSCH can beassociated with a second TCI state. The first TCI state and the secondTCI state can be different.

According to a possible embodiment, the first indication can be controlinformation regarding a URLLC communication between the first set ofTRPs and the UE. The Kmin value can be zero. For example, if the UEreceives a PDSCH or PDCCH scheduling a PDSCH, that can be implicitly beconsidered the first indication, and the indicated Kmin value can bezero, such as when the UE receives information regarding scheduling of aURLLC communication, the UE can assume the Kmin value is indicated to bezero.

According to a possible embodiment, a backhaul between the first set ofTRPs and the second set of TRPs can be determined to be non-ideal. Thesecond indication can be indicated to the at least one second TRP of thesecond set of TRPs of the network in response to determining thebackhaul between the first set of TRPs and the second set of TRPs isnon-ideal.

FIG. 6 is an example flowchart 600 illustrating the operation of awireless communication device, such as the network entity 120, accordingto a possible embodiment. At 610, a first indication can be sent from atleast one first transmission reception point of a first set oftransmission reception points of a network. The first indication canindicate a minimum scheduling offset value (Kmin value) betweenscheduling DCI of the first set of transmission reception points and acorresponding data communication.

At 620, a second indication can be received. The second indication cancorrespond to at least one second transmission reception point of asecond set of transmission reception points of the network. The secondindication can indicate the Kmin value.

At 630, a first scheduling DCI can be transmitted. The first schedulingDCI can schedule a first corresponding data communication associatedwith the first set of transmission reception points.

At 640, a second scheduling DCI can be transmitted. The secondscheduling DCI can schedule a second corresponding data communicationassociated with the second set of TRPs.

At 650, the first corresponding data communication can be communicatedbetween the first set of TRPs of the network and a UE such that theoffset between the first scheduling DCI and the first corresponding datacommunication is at least the Kmin value.

At 660, the second corresponding data communication can be communicatedbetween the second set of TRPs of the network and the UE such that theoffset between the second scheduling DCI and the second correspondingdata communication is at least the Kmin value.

It should be understood that, notwithstanding the particular steps asshown in the figures, a variety of additional or different steps can beperformed depending upon the embodiment, and one or more of theparticular steps can be rearranged, repeated or eliminated entirelydepending upon the embodiment. Also, some of the steps performed can berepeated on an ongoing or continuous basis simultaneously while othersteps are performed. Furthermore, different steps can be performed bydifferent elements or in a single element of the disclosed embodiments.

According to a possible embodiment, a method can be performed at a UE.The method can include reporting to a network, a set of minimumscheduling offset values for cross-slot scheduling for power savingassociated with a value for a maximum number of TRPs.

According to a possible implementation, the set of minimum schedulingoffset values can include a first set of minimum scheduling offsetvalues associated with a first value for the maximum number of TRPs. Theset of minimum scheduling offset values can include a second set ofminimum scheduling offset values associated with a second value for themaximum number of TRPs. The first set of minimum scheduling offsetvalues and the second set of minimum scheduling offset values can bedifferent.

According to a possible implementation, the first value for the maximumnumber of TRPs can be one and the second value for the maximum number ofTRPs can be two.

According to a possible implementation, maximum number of TRPs can bedetermined based on a maximum number of CORESETs for PDCCH monitoringand/or based on a maximum number of simultaneous PDSCH receptions withdifferent TCI states.

According to a possible implementation, the maximum number of TRPs canbe determined based on a maximum number of CORESETs with different TCIstates.

FIG. 7 is an example block diagram of an apparatus 700, such as the UE110, the network entity 120, or any other wireless communication devicedisclosed herein, according to a possible embodiment. The apparatus 700can include a housing 710, a controller 720 coupled to the housing 710,audio input and output circuitry 730 coupled to the controller 720, adisplay 740 coupled to the controller 720, a memory 750 coupled to thecontroller 720, a user interface 760 coupled to the controller 720, atransceiver 770 coupled to the controller 720, at least one antenna 775coupled to the transceiver 770, and a network interface 780 coupled tothe controller 720. The apparatus 700 may not necessarily include all ofthe illustrated elements for different embodiments of the presentdisclosure. The apparatus 700 can perform the methods described in allthe embodiments.

The display 740 can be a viewfinder, a Liquid Crystal Display (LCD), aLight Emitting Diode (LED) display, an Organic Light Emitting Diode(OLED) display, a plasma display, a projection display, a touch screen,or any other device that displays information. The transceiver 770 canbe one or more transceivers that can include a transmitter and/or areceiver. The audio input and output circuitry 730 can include amicrophone, a speaker, a transducer, or any other audio input and outputcircuitry. The user interface 760 can include a keypad, a keyboard,buttons, a touch pad, a joystick, a touch screen display, anotheradditional display, or any other device useful for providing aninterface between a user and an electronic device. The network interface780 can be a Universal Serial Bus (USB) port, an Ethernet port, aninfrared transmitter/receiver, an IEEE 1394 port, a wirelesstransceiver, a WLAN transceiver, or any other interface that can connectan apparatus to a network, device, and/or computer and that can transmitand receive data communication signals. The memory 750 can include aRandom-Access Memory (RAM), a Read Only Memory (ROM), an optical memory,a solid-state memory, a flash memory, a removable memory, a hard drive,a cache, or any other memory that can be coupled to an apparatus.

The apparatus 700 or the controller 720 may implement any operatingsystem, such as Microsoft Windows®, UNIX®, LINUX®, Android™, or anyother operating system. Apparatus operation software may be written inany programming language, such as C, C++, Java, or Visual Basic, forexample. Apparatus software may also run on an application framework,such as, for example, a Java® framework, a NET framework, or any otherapplication framework. The software and/or the operating system may bestored in the memory 750, elsewhere on the apparatus 700, in cloudstorage, and/or anywhere else that can store software and/or anoperating system. The apparatus 700 or the controller 720 may also usehardware to implement disclosed operations. For example, the controller720 may be any programmable processor. Furthermore, the controller 720may perform some or all of the disclosed operations. For example, atleast some operations can be performed using cloud computing and thecontroller 720 may perform other operations. At least some operationscan also be performed computer executable instructions executed by atleast one computer processor. Disclosed embodiments may also beimplemented on a general-purpose or a special purpose computer, aprogrammed microprocessor or microprocessor, peripheral integratedcircuit elements, an application-specific integrated circuit or otherintegrated circuits, hardware/electronic logic circuits, such as adiscrete element circuit, a programmable logic device, such as aprogrammable logic array, field programmable gate-array, or the like. Ingeneral, the controller 720 may be any controller or processor device ordevices capable of operating an apparatus and implementing the disclosedembodiments. Some or all of the additional elements of the apparatus 700can also perform some or all of the operations of the disclosedembodiments.

In operation, the apparatus 700 can perform the methods and operationsof the disclosed embodiments. The transceiver 770 can transmit andreceive signals, including data signals and control signals that caninclude respective data and control information. The controller 720 cangenerate and process the transmitted and received signals andinformation.

In operation according to a possible embodiment, the controller 720 candetermine a minimum scheduling offset value (Kmin) between schedulingDCI and a corresponding data communication based on a control channelconfiguration. The transceiver 770 can receive particular scheduling DCIscheduling a particular corresponding data communication.

The controller 720 can determine whether the determined Kmin value isapplicable to the particular scheduling DCI and the particularcorresponding data communication. The transceiver 770 can communicate,in response to determining the determined Kmin value is applicable tothe particular scheduling DCI and the particular corresponding datacommunication, the corresponding data communication with a network suchthat the offset between the particular scheduling DCI and the particularcorresponding data communication is at least the determined Kmin value.

According to a possible embodiment, the control channel configurationcan be a maximum number of CORESETs in a PDCCH configuration, alimitation on number of PDCCH blind decodes, a limitation on number ofCCEs for PDCCH monitoring, and/or any other control channelconfiguration.

According to a possible embodiment, the determined Kmin value can befurther determined based on an indication from the network.

According to a possible embodiment, the transceiver 770 can indicate tothe network that the apparatus 700 is capable of power saving using afirst set of Kmin values associated with a first control channelparameter and using a second set of Kmin values associated with a secondcontrol channel parameter. The determined Kmin value can be determinedbased on the first set of Kmin values and the second set of Kmin values.

According to a possible embodiment, the particular scheduling DCI canindicate a scheduling offset (K) to apply between the particularscheduling DCI and the particular corresponding data communication. Thedetermined Kmin value can be applicable to the particular scheduling DCIand the particular corresponding data communication if the schedulingoffset (K) is equal to or larger than the determined Kmin value.

According to a possible embodiment, the transceiver 770 can receive apriority indication in the particular scheduling DCI. The controller 720can determine the determined Kmin value is not applicable to theparticular scheduling DCI and the particular corresponding datacommunication. In response to determining the determined Kmin value isnot applicable to the particular scheduling DCI and the particularcorresponding data communication, the transceiver 770 can communicatethe particular corresponding data communication with the network suchthat the offset between the particular scheduling DCI and the particularcorresponding data communication is smaller than the determined Kminvalue.

In operation according to a possible embodiment, the transceiver 770 canreceive a first indication from at least one first TRP of a first set ofTRPs of a network. The first indication can indicate a minimumscheduling offset value (Kmin value) between scheduling DCI of the firstset of TRPs and a corresponding data communication. The transceiver 770can indicate a second indication to at least one second TRP of a secondset of TRPs of the network. The second indication can indicate the Kminvalue. The transceiver 770 can receive a first scheduling DCI schedulinga first corresponding data communication associated with the first setof TRPs. The transceiver 770 can receive a second scheduling DCIscheduling a second corresponding data communication associated with thesecond set of TRPs.

The transceiver 770 can communicate the first corresponding datacommunication with the first set of TRPs of the network such that theoffset between the first scheduling DCI and the first corresponding datacommunication is at least the Kmin value. The transceiver 770 cancommunicate the second corresponding data communication with the secondset of TRPs of the network such that the offset between the secondscheduling DCI and the second corresponding data communication is atleast the Kmin value.

According to a possible embodiment, the first scheduling DCI can bereceived in a first CORESET of a first set of CORESETs. The secondscheduling DCI can be received in a second CORESET of a second set ofCORESETs. The first set of CORESETs and the second set of CORESETs canbe different.

According to a possible embodiment, the second indication can beindicated via a physical layer uplink control channel (PUCCH).

According to a possible embodiment, the first corresponding datacommunication can be a first PDSCH data transmission. The secondcorresponding data communication can be a second PDSCH datatransmission.

According to a possible embodiment, the first corresponding datacommunication can be a first PUSCH data transmission. The secondcorresponding data communication can be a second PUSCH datatransmission.

According to a possible embodiment, the first scheduling DCI schedulingcan be received in a slot. The second scheduling DCI can be received inthe same slot as the first scheduling DCI.

According to a possible embodiment, the first corresponding datacommunication can be communicated in a slot. The second correspondingdata communication can be communicated in the same slot as the firstcorresponding data communication.

At least some methods of this disclosure can be implemented on aprogrammed processor. However, the controllers, flowcharts, and modulesmay also be implemented on a general purpose or special purposecomputer, a programmed microprocessor or microcontroller and peripheralintegrated circuit elements, an integrated circuit, a hardwareelectronic or logic circuit such as a discrete element circuit, aprogrammable logic device, or the like. In general, any device on whichresides a finite state machine capable of implementing the flowchartsshown in the figures may be used to implement the processor functions ofthis disclosure.

At least some embodiments can improve operation of the discloseddevices. Also, while this disclosure has been described with specificembodiments thereof, it is evident that many alternatives,modifications, and variations will be apparent to those skilled in theart. For example, various components of the embodiments may beinterchanged, added, or substituted in the other embodiments. Also, allof the elements of each figure are not necessary for operation of thedisclosed embodiments. For example, one of ordinary skill in the art ofthe disclosed embodiments would be enabled to make and use the teachingsof the disclosure by simply employing the elements of the independentclaims. Accordingly, embodiments of the disclosure as set forth hereinare intended to be illustrative, not limiting. Various changes may bemade without departing from the spirit and scope of the disclosure.

In this document, relational terms such as “first,” “second,” and thelike may be used solely to distinguish one entity or action from anotherentity or action without necessarily requiring or implying any actualsuch relationship or order between such entities or actions. The phrase“at least one of,” “at least one selected from the group of,” or “atleast one selected from” followed by a list is defined to mean one,some, or all, but not necessarily all of, the elements in the list. Theterms “comprises,” “comprising,” “including,” or any other variationthereof, are intended to cover a non-exclusive inclusion, such that aprocess, method, article, or apparatus that comprises a list of elementsdoes not include only those elements but may include other elements notexpressly listed or inherent to such process, method, article, orapparatus. An element proceeded by “a,” “an,” or the like does not,without more constraints, preclude the existence of additional identicalelements in the process, method, article, or apparatus that comprisesthe element. Also, the term “another” is defined as at least a second ormore. The terms “including,” “having,” and the like, as used herein, aredefined as “comprising.” Furthermore, the background section is notadmitted as prior art, is written as the inventor's own understanding ofthe context of some embodiments at the time of filing, and includes theinventor's own recognition of any problems with existing technologiesand/or problems experienced in the inventor's own work.

We claim:
 1. A method at a user equipment, the method comprising:receiving a first indication from at least one first transmissionreception point of a first set of transmission reception points of anetwork, the first indication indicating a minimum scheduling offsetvalue (Kmin value) between scheduling downlink control information ofthe first set of transmission reception points and a corresponding datacommunication; indicating a second indication to at least one secondtransmission reception point of a second set of transmission receptionpoints of the network, the second indication indicating the Kmin value;receiving a first scheduling downlink control information scheduling afirst corresponding data communication associated with the first set oftransmission reception points; receiving a second scheduling downlinkcontrol information scheduling a second corresponding data communicationassociated with the second set of transmission reception points;communicating the first corresponding data communication with the firstset of transmission reception points of the network such that a firstoffset between the first scheduling downlink control information and thefirst corresponding data communication is at least the Kmin value; andcommunicating the second corresponding data communication with thesecond set of transmission reception points of the network such that asecond offset between the second scheduling downlink control informationand the second corresponding data communication is at least the Kminvalue.
 2. The method according to claim 1, wherein the first schedulingdownlink control information is received in a first control resource setof a first set of control resource sets, wherein the second schedulingdownlink control information is received in a second control resourceset of a second set of control resource sets, and wherein the first setof control resource sets and the second set of control resource sets aredifferent.
 3. The method according to claim 2, wherein the first controlresource set is associated with a first transmission configurationindication state, wherein the second control resource set is associatedwith a second transmission configuration indication state, and whereinthe first transmission configuration indication state and the secondtransmission configuration indication state are different.
 4. The methodaccording to claim 1, wherein the second indication is indicated via aphysical layer uplink control channel.
 5. The method according to claim1, wherein the first corresponding data communication is a firstphysical downlink shared channel data transmission, and wherein thesecond corresponding data communication is a second physical downlinkshared channel data transmission.
 6. The method according to claim 5,wherein the first downlink physical downlink shared channel isassociated with a first transmission configuration indication state,wherein the second downlink physical downlink shared channel isassociated with a second transmission configuration indication state,and wherein the first transmission configuration indication state andthe second transmission configuration indication state are different. 7.The method according to claim 1, wherein the first corresponding datacommunication is a first physical uplink shared channel datatransmission, and wherein the second corresponding data communication isa second physical uplink shared channel data transmission.
 8. The methodaccording to claim 1, wherein the Kmin value is zero.
 9. The methodaccording to claim 1, wherein the Kmin value is greater than zero. 10.The method according to claim 1, wherein the first scheduling downlinkcontrol information scheduling is received in a slot, and wherein thesecond scheduling downlink control information is received in the sameslot as the first scheduling downlink control information.
 11. Themethod according to claim 1, wherein the first corresponding datacommunication is communicated in a slot, and wherein the secondcorresponding data communication is communicated in the same slot as thefirst corresponding data communication.
 12. The method according toclaim 1, wherein the first indication comprises control informationregarding an ultra-reliable low latency communication between the firstset of transmission reception points and the user equipment, and whereinthe Kmin value is zero.
 13. An apparatus comprising: a controller thatcontrols operations of the apparatus; and a transceiver coupled to thecontroller, where the transceiver receives a first indication from atleast one first transmission reception point of a first set oftransmission reception points of a network, the first indicationindicating a minimum scheduling offset value (Kmin value) betweenscheduling downlink control information of the first set of transmissionreception points and a corresponding data communication, indicates asecond indication to at least one second transmission reception point ofa second set of transmission reception points of the network, the secondindication indicating the Kmin value, receives a first schedulingdownlink control information scheduling a first corresponding datacommunication associated with the first set of transmission receptionpoints, receives a second scheduling downlink control informationscheduling a second corresponding data communication associated with thesecond set of transmission reception points, communicates the firstcorresponding data communication with the first set of transmissionreception points of the network such that a first offset between thefirst scheduling downlink control information and the firstcorresponding data communication is at least the Kmin value, andcommunicates the second corresponding data communication with the secondset of transmission reception points of the network such that a secondoffset between the second scheduling downlink control information andthe second corresponding data communication is at least the Kmin value.14. The apparatus according to claim 13, wherein the first schedulingdownlink control information is received in a first control resource setof a first set of control resource sets, wherein the second schedulingdownlink control information is received in a second control resourceset of a second set of control resource sets, and wherein the first setof control resource sets and the second set of control resource sets aredifferent.
 15. The apparatus according to claim 13, wherein the secondindication is indicated via a physical layer uplink control channel. 16.The apparatus according to claim 13, wherein the first correspondingdata communication is a first physical downlink shared channel datatransmission, and wherein the second corresponding data communication isa second physical downlink shared channel data transmission.
 17. Theapparatus according to claim 13, wherein the first corresponding datacommunication is a first physical uplink shared channel datatransmission, and wherein the second corresponding data communication isa second physical uplink shared channel data transmission.
 18. Theapparatus according to claim 13, wherein the first scheduling downlinkcontrol information scheduling is received in a slot, and wherein thesecond scheduling downlink control information is received in the sameslot as the first scheduling downlink control information.
 19. Theapparatus according to claim 13, wherein the first corresponding datacommunication is communicated in a slot, and wherein the secondcorresponding data communication is communicated in the same slot as thefirst corresponding data communication.